Skip to content

docs: require PLAN currency checks in reviews - #1588

Merged
mergify[bot] merged 2 commits into
mainfrom
codex/agents-plan-review
Oct 15, 2026
Merged

mergify[bot] merged 2 commits into
mainfrom
codex/agents-plan-review

Conversation

@Cuarroc

@Cuarroc Cuarroc commented Oct 15, 2026 •

Copy link
Copy Markdown
Owner

Die Review-Hinweise zu PR #1588 sind umgesetzt: der Plan enthält jetzt die Paketzeile, und die beiden Dokumentationsdetails sind korrigiert. Damit ist die PLAN-Aktualitätsprüfung samt Paket-ID auch im PR-Template verankert. Du musst nichts weiter entscheiden.

Report

Plan-ID: AGENTS-PLAN-REVIEW

What changed

  • Added the AGENTS-PLAN-REVIEW row to docs/PLAN.md with the requested goal, owner, and merged status.
  • Restored base indentation in AGENTS.md (whitespace only).
  • Added Plan-ID: <PLAN-ID> directly below ## Report in the PR template.

Review disposition

Finding Disposition
R1588-P1 Accepted; PLAN row added in commit aecad6d15b80e70b7352127de434a56fe5b90493.
R1588-L1 Accepted; accidental indentation removed in commit aecad6d15b80e70b7352127de434a56fe5b90493.
R1588-L2 Accepted; Plan-ID template line added in commit aecad6d15b80e70b7352127de434a56fe5b90493.

Evidence

Command Exit code
npm run dev:agent-check 0 (15 ok, 4 optional warnings, 0 failures)
bash scripts/ci/gates.sh lane prepush 0
bash scripts/ci/secret-scan.sh 0 (no leaks found)
`test "$(git diff origin/main...HEAD grep '^+'
grep -n AGENTS-PLAN-REVIEW docs/PLAN.md 0
git ls-remote origin codex/agents-plan-review 0; remote SHA aecad6d15b80e70b7352127de434a56fe5b90493

NICHT ABGEDECKT

  • Linux does not compile or run #[cfg(windows)] tests or Windows clippy arms. The Windows verdict remains for the merge queue.
  • External services are not exercised by this documentation-only change.

Review

Review: ausstehend (Stufe C).

No-Test: documentation of a review rule
@Cuarroc
Cuarroc marked this pull request as ready for review October 15, 2026 19:06
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-15T19:32:45.477399Z aecad6d New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 23f24d3665

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread AGENTS.md
changes invalidate the affected evidence, so review the delta again. A finding
without `file:line` counts as unproven.

Every review checks `docs/PLAN.md` at the head: the PR's own row (identified by `Plan-ID:`) states what is true after merge, and changes in the PR leave no other row, the user section or decision inbox stale; cross-check against `gh`. A mismatch is a medium finding, or high if the user section asks for something already done, and must be fixed in the same PR before `review-ok` (user order 2026-10-15: the plan must never be stale).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Ergänze dieses Paket im kanonischen Plan

Am geprüften Head enthält docs/PLAN.md keine Zeile für die im Commit-Bericht genannte Plan-ID: AGENTS-PLAN-REVIEW; der Bericht verschiebt diesen Eintrag ausdrücklich auf einen späteren Sync. Damit verletzt bereits dieser PR die neu eingeführte Pflicht, den eigenen Planeintrag im selben PR aktuell zu halten, und review-ok dürfte nach dieser Regel nicht vergeben werden. Ergänze den Eintrag in diesem Paket, statt ihn zu vertagen.

AGENTS.md reference: AGENTS.md:L121-L121

Useful? React with 👍 / 👎.

Comment thread AGENTS.md
changes invalidate the affected evidence, so review the delta again. A finding
without `file:line` counts as unproven.

Every review checks `docs/PLAN.md` at the head: the PR's own row (identified by `Plan-ID:`) states what is true after merge, and changes in the PR leave no other row, the user section or decision inbox stale; cross-check against `gh`. A mismatch is a medium finding, or high if the user section asks for something already done, and must be fixed in the same PR before `review-ok` (user order 2026-10-15: the plan must never be stale).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Füge die Plan-ID in die PR-Vorlage ein

Wenn ein Autor die kanonische .github/pull_request_template.md verwendet, enthält der erzeugte Bericht nur **Package:** <ID from docs/PLAN.md> und keine eigenständige Plan-ID:-Zeile. Die neue Regel verlangt jedoch genau diesen Marker zur Identifikation des eigenen Planeintrags, und die vorhandenen PLAN-Auswerter erkennen im PR-Text ebenfalls nur Zeilen im Format Plan-ID: (scripts/lib/plan-model.mjs:102, scripts/lib/roadmap-data.mjs:26). Ohne gleichzeitige Anpassung der Vorlage erfüllen regulär erstellte PR-Berichte die neue Konvention nicht zuverlässig.

AGENTS.md reference: AGENTS.md:L283-L284

Useful? React with 👍 / 👎.

@Cuarroc Cuarroc added the review-ok Pipeline: review disposition complete, no open high finding label Oct 15, 2026
@Cuarroc

Cuarroc commented Oct 15, 2026

Copy link
Copy Markdown
Owner Author

Root: review-ok bound to head 23f24d3 (tier C, gates suffice; all checks pass incl. CodeQL and GitGuardian, 2026-10-15 21:15:03 ).

@Cuarroc

Cuarroc commented Oct 15, 2026

Copy link
Copy Markdown
Owner Author

Root auto-queue: head 23f24d3 unchanged since review-ok, all checks green. @Mergifyio queue

@mergify mergify Bot added the queued label Oct 15, 2026
@mergify mergify Bot mentioned this pull request Oct 15, 2026
21 of 51 tasks
@Cuarroc Cuarroc removed the review-ok Pipeline: review disposition complete, no open high finding label Oct 15, 2026
@Cuarroc

Cuarroc commented Oct 15, 2026

Copy link
Copy Markdown
Owner Author

Root: review-ok removed (2026-10-15 21:18:51 ). Root set it without reading the server review (reports/review-pr1588-claude, Sonnet 5.5, non-author family): APPROVE WITH CONDITIONS, R1588-P1 (medium, PLAN row AGENTS-PLAN-REVIEW missing). That condition is exactly the rule this PR introduces, so it is fixed in this PR first (plus L1 whitespace, L2 template Plan-ID: line).

@mergify

mergify Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • ✅ Entered queue — 2026-10-15 19:15 UTC · Rule: default · triggered by merge protections
  • 🟠 Checks running · on draft merge queue: checking #1588 on main (c9d4ca3) #1589
  • 🚫 Left the queue — 2026-10-15 19:19 UTC · at 23f24d3665be52da9f9438449d2087b6e5de5672

This pull request spent 4 minutes 15 seconds in the queue, with no time running CI.

Reason

Pull request #1588 has been dequeued

Queue conditions are not satisfied:

  • all of: [🚦 Auto-merge conditions]
    • label = review-ok
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue rule default]
      • label = review-ok

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Waiting for
  • check-success = gates (linux)
  • check-success = gates (windows)
  • check-success = red-first
  • any of: [🛡 GitHub repository ruleset rule main-pr-required-checks]
    • check-neutral = @github-actions/gates (linux)
    • check-skipped = @github-actions/gates (linux)
    • check-success = @github-actions/gates (linux)
  • any of: [🛡 GitHub repository ruleset rule main-pr-required-checks]
    • check-neutral = @github-actions/gates (windows)
    • check-skipped = @github-actions/gates (windows)
    • check-success = @github-actions/gates (windows)
  • any of: [🛡 GitHub repository ruleset rule main-pr-required-checks]
    • check-neutral = @github-actions/red-first
    • check-skipped = @github-actions/red-first
    • check-success = @github-actions/red-first
All conditions
  • check-success = gates (linux)
  • check-success = gates (windows)
  • check-success = red-first
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @github-actions/gates (linux)
    • check-skipped = @github-actions/gates (linux)
    • check-success = @github-actions/gates (linux)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @github-actions/gates (windows)
    • check-skipped = @github-actions/gates (windows)
    • check-success = @github-actions/gates (windows)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @github-actions/red-first
    • check-skipped = @github-actions/red-first
    • check-success = @github-actions/red-first
  • github-review-approved [🛡 GitHub repository ruleset rule main-pr-required-checks]
  • label != do-not-merge
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections

Requeued — the merge queue status continues in this comment ↓.

@mergify mergify Bot added dequeued and removed queued labels Oct 15, 2026
No-Test: documentation-only review follow-up
@mergify mergify Bot removed the dequeued label Oct 15, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: aecad6d15b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/PLAN.md
| ID | Ziel | Abhängigkeit | Status |
|---|---|---|---|
| PLAN-AUTO-1 | PLAN-Modell + `npm run plan:check` (Befunde: PR ohne Planzeile, Status widerspricht GitHub, unbekannte Abhängigkeit, Job ohne Zeile, Entscheidung ohne Zeile, Plan veraltet) | – | läuft: Draft-PR #1564, 15.10. (`gh pr list --search "PLAN-AUTO-1"`) |
| AGENTS-PLAN-REVIEW | Reviews prüfen PLAN-Aktualität (eigene Zeile über Plan-ID, Nutzerbereich, Entscheidungs-Eingang gegen gh) | Root | Erledigt mit Merge von PR #1588 |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Korrigiere Root als vermeintliche Abhängigkeit

In dieser vier Spalten umfassenden Tabelle ist das dritte Feld Abhängigkeit, nicht Owner; dadurch behauptet der kanonische Plan nach dem Merge, dass das Paket von einer Person namens Root abhängt, obwohl keine Paketabhängigkeit besteht. Ersetze den Wert durch – oder ergänze eine echte Owner-Spalte, damit die eigene Planzeile den Zustand korrekt beschreibt.

AGENTS.md reference: AGENTS.md:L121-L121

Useful? React with 👍 / 👎.

Comment thread docs/PLAN.md
| ID | Ziel | Abhängigkeit | Status |
|---|---|---|---|
| PLAN-AUTO-1 | PLAN-Modell + `npm run plan:check` (Befunde: PR ohne Planzeile, Status widerspricht GitHub, unbekannte Abhängigkeit, Job ohne Zeile, Entscheidung ohne Zeile, Plan veraltet) | – | läuft: Draft-PR #1564, 15.10. (`gh pr list --search "PLAN-AUTO-1"`) |
| AGENTS-PLAN-REVIEW | Reviews prüfen PLAN-Aktualität (eigene Zeile über Plan-ID, Nutzerbereich, Entscheidungs-Eingang gegen gh) | Root | Erledigt mit Merge von PR #1588 |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Vermeide einen Done-Status vor dem Merge

Solange PR #1588 offen ist, normalisiert normalizeStatus() den führenden Text Erledigt als done; checkPlan() meldet für diese mit #1588 verknüpfte Zeile deshalb status-contradicts-github (done / GitHub OPEN). Damit erzeugt der neu vorgeschriebene Abgleich am Review-Head selbst einen Befund und verhindert nach der neuen Regel review-ok; erfasse den aktuellen Zustand als In Prüfung oder lehre den Prüfer, die Formulierung als bedingten Nach-Merge-Status zu behandeln.

AGENTS.md reference: AGENTS.md:L121-L121

Useful? React with 👍 / 👎.

Comment thread AGENTS.md
changes invalidate the affected evidence, so review the delta again. A finding
without `file:line` counts as unproven.

Every review checks `docs/PLAN.md` at the head: the PR's own row (identified by `Plan-ID:`) states what is true after merge, and changes in the PR leave no other row, the user section or decision inbox stale; cross-check against `gh`. A mismatch is a medium finding, or high if the user section asks for something already done, and must be fixed in the same PR before `review-ok` (user order 2026-10-15: the plan must never be stale).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Beschränke die eigene Planzeile auf Paket-PRs

Bei Dependabot- und anderen Nicht-Paket-PRs existiert absichtlich keine eigene Plan-ID:-Zeile: checkPlan() fordert sie nur für Anbieter-Paketbranches, und PLAN-AUTO-2 beschreibt ebenfalls nur Paket-PRs. Die Formulierung „Every review“ macht das Fehlen nun trotzdem zu einem vor review-ok zu behebenden Mismatch; weil kein Branchtyp von review-ok ausgenommen ist, lassen sich solche Wartungs-PRs regelkonform nicht mehr einreihen. Beschränke daher nur die Own-row-Klausel auf Paket-PRs, während die allgemeine Aktualitätsprüfung für alle Reviews gelten kann.

AGENTS.md reference: AGENTS.md:L352-L361

Useful? React with 👍 / 👎.

@Cuarroc Cuarroc added the review-ok Pipeline: review disposition complete, no open high finding label Oct 15, 2026
@Cuarroc

Cuarroc commented Oct 15, 2026

Copy link
Copy Markdown
Owner Author

Root: review-ok bound to head aecad6d (2026-10-15 21:39:29 ). Review reports/review-pr1588-claude (Sonnet 5.5, Anthropic; author Codex/OpenAI): APPROVE on this head, conditions R1588-P1/L1/L2 fixed. R1588-P2 (low, row placement / 'Root' in dependency column): follow-up in PLAN-CLEAN. All checks pass incl. CodeQL and GitGuardian.

@Cuarroc

Cuarroc commented Oct 15, 2026

Copy link
Copy Markdown
Owner Author

Root auto-queue: head aecad6d unchanged since review-ok, all checks green. @Mergifyio queue

@mergify mergify Bot added the queued label Oct 15, 2026
@mergify mergify Bot mentioned this pull request Oct 15, 2026
30 of 46 tasks
@mergify
mergify Bot merged commit c7a43fb into main Oct 15, 2026
18 checks passed
@mergify

mergify Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • ✅ Entered queue — 2026-10-15 19:40 UTC · Rule: default · triggered by merge protections
  • ✅ Checks passed · on draft merge queue: checking #1588 on main (c9d4ca3) #1590
  • ✅ Merged — 2026-10-15 19:54 UTC · at c7a43fbd0cf6e9e750819b32f3c9e0676c8ac7f0 · merge

This pull request spent 14 minutes 18 seconds in the queue, including 13 minutes 35 seconds running CI.

Required conditions to merge
  • check-success = gates (linux)
  • check-success = gates (windows)
  • check-success = red-first
  • github-review-approved [🛡 GitHub repository ruleset rule main-pr-required-checks]
  • label != do-not-merge
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (linux)
    • check-neutral = @github-actions/gates (linux)
    • check-skipped = @github-actions/gates (linux)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (windows)
    • check-neutral = @github-actions/gates (windows)
    • check-skipped = @github-actions/gates (windows)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/red-first
    • check-neutral = @github-actions/red-first
    • check-skipped = @github-actions/red-first
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections

@mergify
mergify Bot deleted the codex/agents-plan-review branch October 15, 2026 19:54
@mergify mergify Bot removed the queued label Oct 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review-ok Pipeline: review disposition complete, no open high finding

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant